Usenet 1993 July

home *** CD-ROM | disk | FTP | other *** search

/ Usenet 1993 July / InfoMagic USENET CD-ROM July 1993.ISO / answers / os2-faq / user / part3 < prev next >

Wrap

Text File | 1993-06-14 | 55.2 KB | 1,329 lines

Newsgroups: comp.os.os2.misc,comp.os.os2.apps,news.answers,comp.answers Path: senator-bedfellow.mit.edu!enterpoop.mit.edu!gatech!howland.reston.ans.net!ux1.cso.uiuc.edu!uchinews!kimbark!sip1 From: sip1@kimbark.uchicago.edu (Timothy F. Sipples) Subject: OS/2 Frequently Asked Questions List Rel. 2.1A (3 of 4) Message-ID: <1993Jun14.063756.26179@midway.uchicago.edu> Followup-To: comp.os.os2.misc Sender: news@uchinews.uchicago.edu (News System) Supersedes: <1993Apr25.184224.15006@midway.uchicago.edu> Reply-To: sip1@midway.uchicago.edu Organization: University of Chicago Computing Organizations Date: Mon, 14 Jun 1993 06:37:56 GMT Approved: news-answers-request@mit.edu Expires: Sun, 15 Aug 1993 23:59:59 GMT Lines: 1312 Xref: senator-bedfellow.mit.edu comp.os.os2.misc:65777 comp.os.os2.apps:16846 news.answers:9357 comp.answers:986 Archive-name: os2-faq/user/part3 Version: 2.1A [Part 3 of 4] International OS/2 User Group by phoning 285-641175 in the U.K.) The OS/2 Device Driver Source Kit CD-ROM is also now available from IBM, part no. 71G3703. To order phone 407-982-4239 (FAX 407-982-4218) in North America, 61-2-354-7684 (FAX 61-2-354-7766) in most of the Far East and Pacific Rim, 81-3-5563-5897 (FAX 81-3-5563-4957) in Japan, 81-2-528-1548 (FAX 82-2-528-1414) in Korea, or 011-52-627-1846 (FAX 011-52-395-7812) in Latin America. IBM offers classes worldwide to help in using and programming OS/2 2.1; phone your local IBM branch office (or the OS/2 Hotline) for more information. Or contact one of these third party providers of classes training materials: Company Telephone Acumen People and Productivity 61-3-853-6662 Adaptive Research and Design 305-889-0070 Adar International 212-750-5820 Allied Computer Service Singapore 2948741 AOSI 415-586-3454 Applied Learning 708-369-3000 ATI 310-823-1129 Ron Beauchemin 203-285-5896 Bell and Associates 61-2-953-7619 Broadway and Seymour 800-274-9287 Chapman and Associates 714-831-4442 Charles Hatvany and Associates 617-648-4100 CIE 800-882-3981 Computer Information Associates 708-766-4677 Computer Training Center 901-753-9706 CompuTrainers 212-984-0522 Comsell 404-872-2500 Creative Systems Programming 609-234-1500 David Bernstein Company 206-282-8711 Denenfeld Systems Design 519-396-8088 Descriptor Systems 319-362-3906 Development Technologies 803-790-1234 Edutrends 201-838-6700 Chris Eldridge Pty Ltd. 61-2-016-289-093 Electronic Directions 212-213-6500 Fermier Consulting and Education 817-481-4966 Future Enterprises 202-662-7676 Gateway Technologies Corp. 203-693-1097 Hailey Griffin Corp. 416-475-4200 Huffman and Associates 805-461-1053 Iconisys 805-522-8863 InfoLink Solutions 404-876-1512 Infotec Training Institute 800-282-7990 Instruction Set 617-890-4930 Instructional Systems Co. 212-477-8800 Instructware 800-267-0101 iQ Training Systems 44-71-613-5771 IS International 407-994-4373 JRT Information Services 407-547-0178 Jensen Enterprises 616-429-9599 Kee Systems 301-880-0880 Kemtex Services 212-661-5770 Knowhow Solutions 61-2-955-9592 Dr. Michael S. Kogan 904-246-8341 Logical Operations 716-482-7700 Management Technology Education 61-2-261-5555 61-3-629-5811 61-7-840-9248 61-8-231-3048 61-9-324-1142 Mannix Enterprises 914-229-8109 Mentor Technologies 614-265-3170 Microtransfer 44-869-50340 Minasi and Company 703-276-8940 Object Management Laboratory 818-879-9620 One on One Computer Training 708-628-0500 One Up Corp. 214-620-1123 PC Dialogs 212-663-3459 PC Etcetera 212-736-5870 PCLC 212-953-9800 Professional Development Assoc. Singapore 2272883 Pinnacle Technology 918-455-2520 Productivity Point International 800-848-0980 Productivity Solutions 215-631-5685 Professional Development Assoc. 44-71-706-3744 Progressive Software Technologies 303-932-2051 QED Information Sciences 800-343-4848 Rockey and Assoc. 215-640-4880 SCS Computer Consulting 718-321-1572 Kenneth E. Sanger 914-948-8496 SE International 407-241-3428 Sims Software Technology 415-731-2222 Software Education Corp. 908-946-0606 Software Paradise 44-222-887521 Soza & Company 703-560-9477 Stratemm Pacific Ltd. New Zealand 07-578-5100 Testek 207-539-8825 Touchstone Systems Group 312-263-1444 User View 612-331-7212 ViaGrafix U.S. 918-825-6700 VisGrafix Australia 61-9-417-3178 Wave Technologies Training 214-650-9283 William H. Zack & Assoc. 203-255-2979 Worthman & Assoc. 303-290-9700 For a free copy of the IBM IV League catalog (with OS/2 books, videotapes, and other support materials), phone 800-342-6672. For more information on the IBM IV (Independent Vendor) League, an organization of individuals and companies who develop and market products and services that support OS/2, call 203-262-3769 or 203-262-3776. You may also dial the IV League BBS at 203-380-8264. If you need to reach any individual at IBM, but you do not know that person's direct telephone number, call the IBM Switchboard at 800-IBM-3333. See (4.9) Books and Magazines for information on OS/2 publications. Any of the regular DOS or Windows resources (e.g. books, magazines, shareware/freeware sources) will be useful since both environments come with OS/2 2.1. Related information: (1.3) DOS and Windows Compatibility (3.2) Shareware and Freeware Sources (3.6) Multimedia (4.8) User Groups (4.9) Books and Magazines (4.10) Problem Report Form (4.6) Corrective Service Diskettes What are CSDs, how do I tell which I have, and where do I get them? CSDs are Corrective Service Diskettes, or bug fixes (Service Paks), periodically issued by IBM. The OS/2 CSD level number may be obtained using the command SYSLEVEL from an OS/2 command line prompt. CSDs are cumulative, i.e. only the most recent CSD is required to bring a system up from any previous CSD level. However, CSDs only apply within a major version number. For example, an upgrade, not a CSD, would bring OS/2 Version 2.0 up to Version 2.1. Note also that each national language (e.g. French, U.K. English) uses a distinct CSD. CSDs may be ordered by phoning 800-3-IBM-OS2. Customers with IBM customer numbers (usually large sites) should phone 800-237-5511 or order through IBMLink. Outside the United States, ask an authorized IBM dealer or representative for the CSD. CSDs may also be downloaded from the IBM PC Co. BBS (modem 404-835-6600), CompuServe (FIND OS/2), or from (3.2) Shareware and Freeware Sources. And CSDs may be ordered through IBM's OS/2 BBS. The latest, current OS/2 2.1 CSD level will be listed in this List and in the PS/2 Assistant files. At present there is no Service Pak for OS/2 2.1. Related information: (3.2) Shareware and Freeware Sources (4.7) Online Services Which online services support OS/2, and how do I join? IBM's official non-IBM online service for OS/2 user and developer support is CompuServe (FIND OS/2). In the United States you can obtain CompuServe membership information by phoning 800-848-8199. IBM maintains an unofficial presence on many other networks. For information on the Internet consult one of the many books describing the network. One example: The Whole Internet by Ed Krol, O'Reilly & Associates (phone 707-829-0515), ISBN 1-56592-025-2. Once you start using the Internet you should peruse the information files posted to the news.answers newsgroup to familiarize yourself with Internet resources. The OS/2 Roundtable (Page 1400, Keyword OS2) has opened on GEnie. To subscribe to GEnie, set your communications software to half duplex and either 1200 or 2400 bps then have your modem dial 800-638-8369 (800-387-8330 in Canada). Upon connection, type HHH and press RETURN. At the U#= prompt type SIGNUP and press RETURN, then follow the directions given. See (3.2) Shareware and Freeware Sources, (4.5) Technical Support, and (4.11) OS/2 BBSes for information on other online services with high OS/2 content. Related information: (3.2) Shareware and Freeware Sources (4.5) Technical Support (4.11) OS/2 BBSes (4.8) User Groups Are there any OS/2 user groups? The following OS/2 user groups meet regularly: Northeast Ohio (Akron) OS/2 User Group Contact: Garey Smiley (phone 216-630-3565) Atlanta OS/2 Users Group Contact: Robert Cannon (phone 404-908-2121) Baton Rouge OS/2 Users Group Contact: David Arbour (phone 504-753-9637) North Suburban Chicago OS/2 User's Group Contact: James Schmidt (phone 708-317-7405) Greater Chicago OS/2 User Group Contact: Lisa Der Mateosian (phone 312-245-6418) West Suburban Chicago OS/2 User Group Contact: Dwight Cannon (phone 708-742-0700 ext. 2170) Mid Missouri (Columbia) OS/2 Users Group Contact: Woody Sturges (BBS 314-446-0016) Denver OS/2 User's Group Contact: Ronald Van Iwaarden (BBS 303-744-0373) Computer Users of Erie (Pennsylvania) OS/2 SIG Contact: Tom Kuklinski (phone 814-866-5396) Fort Wayne OS/2 Users Group Contact: Stephen Gutknecht (phone 219-484-0062) Indianapolis OS/2 Users Group Contact: Jay Schultz (phone 317-634-8080) Las Vegas OS/2 User Group Contact: Karu Karunaratne (phone 702-435-0018, BBS 702-433-5535) Long Island OS/2 User's Group Contact: Jeffrey Altman (phone 516-444-3751) Los Angeles OS/2 Users Group Contact: Paul Duncanson (phone 805-584-6721) Minnesota OS/2 User Group Contact: Marcus Krumpholz (phone 612-869-7956, BBS 612-379-8272) Montreal OS/2 Users Group Contact: Gilbert Daigle (phone 514-923-9964) New England OS/2 User Group Contact: Dave Pinard (phone 203-954-1872) Phoenix PC User Group and OS/2 SIG Contact: 602-222-8511 Triangle (Raleigh, North Carolina) OS/2 User Group Contact: Steve Gallagher (phone 919-254-5637) Sacramento OS/2 Users Group Contact: Charlie Kotan (phone 916-641-4007) San Diego OS/2 User Group Contact: Craig Swanson (BBS 619-558-9475) Bay Area (San Francisco) OS/2 User Group Contact: Sanford Rockowitz (phone 415-755-3124) Singapore (NUS) OS/2 User Group Contact: N. Sriram (Internet: swknasri@nuscc.nus.sg) Tampa Bay OS/2 User Group Contact: Paul Wylie (phone 813-786-4567) International OS/2 User Group (based in the U.K.) Contact: Mike Gove (phone +44(0)285-641175 or FAX +44(0)285-640181) Wellington (New Zealand) OS/2 Users' Group Contact: Andrew McMillian (phone 801-4764 days, 233-9123 evenings) Westchester (New York) OS/2 User Group Contact: Patrick Pearce (phone 914-762-8950) [OS/2 user groups: please send information on your group to the author. See (0.0) Introduction and Credits.] See (6.1) Promoting OS/2 for information on IBM assistance to OS/2 user groups. Related information: (0.0) Introduction and Credits (4.5) Technical Support (6.1) Promoting OS/2 (4.9) Books and Magazines What OS/2 books and magazines are available? OS/2 has its own magazines: OS/2 Developer Magazine (phone 800-WANT-OS2 or 708-647-5960, FAX 708-647-0537), OS/2 Monthly (mail 72550.2440@compuserve.com or phone 800-365-2642), Inside OS/2 (phone 502-491-1900), OS/2 Professional (phone 301-770-7302), and the OS/2 Newsletter (phone 714-495-3757). Many OS/2 2.x books can be ordered by calling IBM Fulfillment Headquarters at 800-342-6672. Or you may obtain OS/2 books through most computer book sellers. Here are just a few of the OS/2 2.x books available, with ISBN and IBM Publication Number, if available: o Designing OS/2 Applications, John Wiley & Sons, ISBN 0-471-58889-X, IBM Publication No. SC28-2701. o Easy OS/2, QUE, ISBN 1-56529-145-X. o The Little Book of OS/2: 2.1 Edition, Peachpit Press. o Micro Focus COBOL/2 Workbench for the Application Developer, QED. o OS/2 for Non-Nerds, New Riders, ISBN 1-56205-153-9, IBM Pub. No. SR28-4319. o OS/2 Inside & Out (2.1), Osborne McGraw-Hill. o OS/2 2.x Notebook: The Best of OS/2 Developer Magazine, Van Nostrand Reinhold, ISBN 0-442-01522-4, IBM Pub. No. G362-0015. o OS/2 2.1 Complete, Abacus. o OS/2 2.1 Programming, Osborne McGraw-Hill, ISBN 0-07-881910-5. o OS/2 2.1 Unleashed, Sams, ISBN 0-672-30240-3, IBM Pub. No. SR28-4318. o The Shell Collection: OS/2 2.1 Utilities, Van Nostrand Reinhold. o Stepping Up to OS/2 2.1, Abacus, ISBN 1-55755-185-5. o Ten-Minute Guide to OS/2 2.1, Alpha, ISBN 1-56761-185-0, IBM Pub. No. SR28-4322. o Using OS/2 2.1: Special Edition, QUE, ISBN 1-56529-118-2, IBM Pub. No. SR28-4317. o Your OS/2 Consultant, Sams. o Advanced OS/2 for Programming Managers, John Wiley & Sons. o Dvorak's Guide to OS/2, Random House. o OS/2 for Dummies (2.1), IDG, ISBN 1-878058-76-2. o OS/2 Instant Reference Book, Sybex. o The OS/2 2.1 User's Bible, Abacus. o OS/2 2.1 Power User's Guide, Van Nostrand Reinhold. o Real-World Programming for OS/2, Sams. o Learn OS/2 in a Day, Wordware Publishing. o Micro Focus CICS Option: Developing CICS Applications on the PC, QED. o OS/2: The Workplace Shell, A User's Guide & Tutorial for Release 2.1, Computer Information Associates. o PC Learning Labs Teaches OS/2, Ziff-Davis Press. o Quick Reference Guide for OS/2 2.1, DDC. o Van Wolverton's Guide to OS/2, Random House. IBM's OS/2 "redbooks" (power user guides) are IBM Publication No. GBOF-2254. (To order these and other IBM publications phone your local IBM office and ask for the Librarian or phone 800-765-4IBM.) These redbooks are also available in electronic form [See (3.2) Shareware and Freeware Sources ]. Other OS/2 publications, such as the OS/2 Technical Library, IBM Part No. 10G3356, are available by calling IBM Technical Books at 800-IBM-PCTB. IBM also offers the OS/2 Online Book Collection CD-ROM, part no. 53G2166. This CD-ROM provides nearly all of the OS/2 publications produced by IBM in electronic form. The CD-ROM includes the following titles: o IBM C Set ++ Version 2.0 - IBM WorkFrame/2 Introduction - IBM C/C++ Tools: Browser Introduction - Collection Class Library Reference - IBM C/C++ Tools C Library Reference - IBM C/C++ Tools: C Language Reference - IBM C/C++ Tools: C++ Language Reference - IBM C/C++ Tools: Debugger Introduction - IBM C/C++ Tools: Programming Guide - IBM C/C++ Tools: Standard Class Library Reference - User Interface Class Library Guide - User Interface Class Library Reference - IBM C/C++ Tools: EXTRA Introduction o IBM International Technical Support Center (Red Books) - OS/2 V2.0 Vol 1: Control Program (ITSC) - OS/2 V2.0 Vol 2: DOS and Windows Environment (ITSC) - OS/2 V2.0 Vol 3: PM and Workplace Shell (ITSC) - OS/2 V2.0 Vol 4: Application Development (ITSC) - OS/2 V2.0 Vol 5: Print Subsystem (ITSC) - OS/2 2.1 Technical Update o OS/2 LAN Server Version 2.0 - OS/2 LAN Server Migration Handbook - Problem Determination Reference Volume 1: Problem Determination Guide - Network Administrator Reference Volume 2: Performance Tuning - DOS LAN Requester User's Quick Reference - LAN Server User's Quick Reference - Problem Determination Reference Volume 3: LAN Error Messages - LAN Support Program User's Guide - Network Administrator Reference Volume 1: Planning and Installation Guide - Network Administrator Reference Volume 3: Network Administrator's Tasks - Problem Determination Reference Volume 2: LAN Alerts - DOS LAN Requester Windows User's Guide - OS/2 LAN Server Productivity Aids - Network Administrator Reference Supplement for OS/2 2.0 o OS/2 LAN Server Version 3.0 - PC LAN Program Migration Guide - Problem Determination Reference Volume 1: Problem Determination Guide - Network Administrator Reference Volume 2: Performance Tuning - DLR and DLR Windows User's Quick Reference - OS/2 LAN Requester User's Quick Reference - Problem Determination Reference Volume 3: LAN Error Messages - IBM LAN Support Program User's Guide - Network Administrator Reference Volume 1: Planning and Installation Guide - Network Administrator Reference Volume 3: Network Administrators Tasks - Problem Determination Reference Volume 2: LAN Alerts - OS/2 LAN Server Productivity Aids - LAN Adapter and Protocol Support Configuration Guide - IBM Network Transport Services/2 Redirected Installation and Configuration Guide - Messages and Problem Determination Guide o Multimedia Presentation Manager/2 Version 1.1 - MMPM/2 Application Programming Guide - MMPM Toolkit/2 - CUA Guide to Multimedia User Interface Design - MMPM/2 Programming Reference - OS/2 Multimedia Advantage o Network Transport Services/2 Version 1.0 - LAN Adapter and Protocol Support Configuration Guide - IBM Network Transport Services/2 Redirected Installation and Configuration Guide - Messages and Problem Determination Guide o OS/2 2.0 - OS/2 2.0 Information and Planning Guide - Getting Started with Workplace Shell (White Paper) - Upgrading to OS/2 2.0 (White Paper) - IBM OS/2 2.0 Getting Started - OS/2 2.0 Installation Guide - OS/2 2.0 Quick Reference - OS/2 2.0 Command Reference - IBM OS/2 2.0 Migrating to the OS/2 Workplace Shell - OS/2 2.0 Using the Operating System - Tips and Techniques - OS/2 2.0 Adobe Type Manager for WIN-OS/2 - OS/2 2.0 Compatibility Information - OS/2 2.0 Using Bidirectional Support o OS/2 2.1 - OS/2 2.0 Information and Planning Guide - Getting Started with Workplace Shell (White Paper) - Upgrading to OS/2 2.0 (White Paper) - OS/2 2.1 Using the Operating System - OS/2 2.1 Book Catalog - OS/2 2.1 Installation Guide - OS/2 2.1 Quick Reference - OS/2 2.1 Command Reference - OS/2 2.0 Using Bidirectional Support - OS/2 2.1 Performance Tuning for End Users (White Paper) - OS/2 2.1 Performance Improvements (White Paper) o Operating System/2 2.0 Technical Library - OEM DASD and SCSI Device Driver Support - OS/2 2.0 Programming Guide: Volume III - Getting Started: OS/2 2.1 Toolkit - Getting Started: Toolkit - Information Presentation Facility - Physical Device Driver Reference - Presentation Manager Programming Reference: Volume I - Presentation Manager Programming Reference: Volume II - Presentation Manager Programming Reference: Volume III - Application Design Guide - Procedures Language 2/REXX User's Guide - Presentation Driver Reference - Virtual Device Driver Reference - System Object Model Guide and Reference - OS/2 2.0 Programming Guide: Volume I - OS/2 Programming Guide: Volume II - Bidirectional National Language Support - Control Program Programming Reference - OS/2 2.1 PM Programming Reference: Volume I - OS/2 2.1 PM Programming Reference: Volume II - OS/2 2.1 PM Programming Reference: Volume III - OS/2 2.1 CP Programming Reference - Procedures Language 2/REXX Reference - SAA CUA Advanced Interface Design Reference - SAA CUA Guide to User Interface Design o PL/I Package/2 Version 1.1 - PL/I Package/2 Programming Guide - PL/I Package/2 Language Environment Run-Time Messages - PL/I Package/2 Installation - PL/I Package/2 Language Reference - PL/I Package/2 Reference Summary - PL/I Package/2 Fact Sheet o SAA Common User Access Controls Library/2 Version 1.0 - Common User Access Controls Library/2 Programming Guide - Common User Access Controls Library/2 PM Reference - Common User Access Controls Library/2 Windows Reference o Transmission Control Protocol/Internet Protocol Version 1.2 for OS/2 - IBM TCP/IP Version 1.2 for OS/2: User's Guide - IBM TCP/IP Version 1.2 for OS/2: Installation and Maintenance - IBM TCP/IP Version 1.2 for OS/2: Programmer's Reference - IBM TCP/IP Version 1.2 for OS/2: Quick Reference Guide o Transmission Control Protocol/Internet Protocol Version 1.2.1 for OS/2 - IBM TCP/IP Version 1.2.1 for OS/2: User's Guide - IBM TCP/IP Version 1.2.1 for OS/2: LAN Adapter and Protocol Support - IBM TCP/IP Version 1.2.1 for OS/2: Installation and Maintenance - IBM TCP/IP Version 1.2.1 for OS/2: Programmer's Reference - IBM TCP/IP Version 1.2.1 for OS/2: Quick Reference Guide Related information: (4.5) Technical Support (4.10) Problem Report Form How do I report an OS/2 problem to IBM? If you would like to send an OS/2 bug report to IBM, you may phone IBM at 800-992-4777 (in the U.S.) or you may fill in the OS/2 Problem Report Form and mail it to IBM via CompuServe or the Internet. The Problem Report Form helps IBM solve your problem more quickly, especially if you include all the relevant details. IBM then has to ask fewer questions in order to determine the problem. To use the Problem Report Form, follow these steps: 1. If you are reading the INF version of this List, press CTRL-F. This panel will then be saved to a file named TEXT.TMP. 2. Using a text editor (like the OS/2 System Editor), open either TEXT.TMP or the plain text version of this List. 3. Delete all the extra lines in the file so that only the OS/2 Problem Report Form remains. 4. Fill in all the requested information using your text editor. 5. Save the Form to disk (as file name OS2PROB.TXT for example). 6. Upload the file to CompuServe Mail or the Internet, and send the Form to IBM. (The exact procedure will depend on the service and the software you use.) You may use the Problem Report Form as many times as you need to, but please include only one problem per copy. If you wish, you can use the Defect Report Form found on Page 493 of the OS/2 2.1 Using the Operating System manual instead of this form. ------ Submit an OS/2 Problem Report ------ <<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>> << THIS SUPPORT IS ELIGIBLE FOR U.S. CUSTOMERS ONLY >> <<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Customers should use this form to report a suspected OS/2 DEFECT to IBM support. IBM employees should refer to the OS2DFECT FORUM in IBMPC for instructions on how to report an OS/2 defect. If you have How-to or other questions about OS/2, please refer to these sources: - The OS/2 on-line help and README. - If you have a CompuServe ID, you may submit an item to the appropriate section within the forums under IBMOS2 (GO IBMOS2). - Many bulletin board systems contain user forums where OS/2 users share information and ideas on OS/2. If you have Beta problems or suggestions, please refer to the bottom of this form for the proper reporting procedure. While we appreciate your input, we do not accept Beta problems through the Base defect or ES/LS support ID's. Customers with CompuServe ID's may report problems on CIS in IBM's PSPBETA forum. If you do NOT have a CIS ID, please send the feedback via Internet to the CIS address: 76711.175@compuserve.com. Please provide as much information as possible on your problem. Feel free to add additional space, or remove sections of the form that are not relevant to your problem. CONTACT PERSON: __________________________________ PHONE NUMBER: (___) ___-____ x____ Phone number where you can be FAX NUMBER: (___) ___-____ x____ contacted between 8-5, M-F. Note: Support will normally be handled electronically through CompuServe mail. IBM may contact you via telephone if it appears it will expedite resolution to the problem. Would you rather be contacted by phone? Y _ N _ ONE LINE DESCRIPTION OF THE OS/2 PROBLEM: ___________________________________________________________________ DETAILED PROBLEM DESCRIPTION - If possible, provide step-by-step recreation scenario. Also, please include any fixes or workarounds you may have already tried. __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ Enter any error messages that occur: ________________________________ Select the appropriate answers by placing an "X" in the space indicated. Can you recreate the problem? Y _ N _ Has the problem occurred on more than one system? Y _ N _ OS/2 OPERATING SYSTEM SOFTWARE CONFIGURATION: OS/2 Version 2.1 .........: _ CSD Level: _______ OS/2 Version 2.0 .........: _ CSD Level: _______ OS/2 1.3 Standard Edition : _ CSD Level: _______ OS/2 1.3 Extended Edition : _ CSD Level: _______ NOTE - CSD = Corrective Service Diskette. Use the SYSLEVEL command to determine, if unknown. HARDWARE CONFIGURATION (provide as much as possible): Brand and model of PC: ____________________________________ Microprocessor: Intel _ Other (specify) _______________ Type: 286 _ 386SX _ 386 _ 486SX _ 486 _ Speed: __ MHz Total RAM ....: __ MB Disk drive ...: ____ MB File System: FAT _ HPFS _ Manufacturer: ___________________ Model # _______ Type: IDE _ SCSI _ MFM _ RLL _ Unknown _ Manufacturer and model # of disk controller: ______________________ Manufacturer, revision #, and date of System BIOS: __________________ Manufacturer and model # of video adapter: __________________________ Manufacturer and model # of display: ________________________________ Memory installed on video adapter: _____ EGA _ VGA _ SVGA _ XGA _ Diskette Drive A: 3 1/2" _ 5 1/4" _ Diskette Drive B: 3 1/2" _ 5 1/4" _ List other adapters installed: _____________________ _____________________ _____________________ TRAP INFORMATION - If a TRAP occurs and results in the 16 bit trap display similar to the following, enter any of the register values that you recorded: SESSION TITLE: __________________________________________________ TRAP____ AX=____ BX=____ CX=____ DX=____ BP= ____ SI=____ DI=____ DS=____ ES=____ FLG=____ CS=____ IP=____ SS=____ SP=____ MSW=____ CSLIM=____ SSLIM=___ DSLIM=___ ESLIM=____ CSACC=__ SSACC=__ DSACC=__ ESACC=__ ERRCD=____ ERLIM=____ ERACC=__ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ If a TRAP occurs and results in the 32 bit trap display similar to the following, enter any of the register values that you recorded: TRAP ____ ERRCD=____ ERACC=____ ERLIM=________ EAC=________ EBX=________ ECX=________ EDX=________ ESI=________ EDI=________ EBP=________ FLG=________ CS:EIP=____:________ CSACC=____ CSLIM=________ SS:ESP=____:________ SSACC=____ SSLIM=________ DS=____ DSACC=____ DSLIM=________ CR0=________ ES=____ ESACC=____ ESLIM=________ CR2=________ FS=____ FSACC=____ FSLIM=________ GS=____ GSACC=____ GSLIM=________ THE SYSTEM DETECTED AN INTERNAL PROCESSING ERROR AT LOCATION ##____:________ - ____:____. _____, ____ ________ INTERNAL REVISION _.___, __/__/__ PRINTER - If this is a printer problem, please provide the following: Printer Vendor: __________________ Model ....: ________________ Driver Name ..: __________________ Port Used : ________________ Printer is attached to: Local _ LAN Server _ Host _ COMMUNICATIONS MANAGER - If this is a problem with Communications Manager, please provide answers in this section: OS/2 Extended Services ............: _ CSD Level: _______ OS/2 EE Communications Manager 1.3 : _ CSD Level: _______ Describe your Communications Manager configuration (DFT, T-R, etc): ________________________________________________________________ ________________________________________________________________ LOCAL AREA NETWORK - If this is a local area network problem, please enter information about the LAN involved: LAN SERVER: OS/2 LAN Server Version 1.3 : _ CSD Level: ________ OS/2 LAN Server 2.0 Entry ..: _ CSD Level: ________ OS/2 LAN Server 2.0 Advanced: _ CSD Level: ________ OS/2 LAN Server 3.0 Entry ..: _ CSD Level: ________ OS/2 LAN Server 3.0 Advanced: _ CSD Level: ________ LAN REQUESTER: LAN Server 3.0 Requester....: _ CSD Level: ________ LAN Server 2.0 Requester....: _ CSD Level: ________ OS/2 1.3 Requester..........: _ CSD Level: ________ DOS LAN REQUESTER: LS 3.0 Requester ...........: _ CSD Level: ________ LS 2.0 Requester ...........: _ CSD Level: ________ OS/2 1.3 Requester .........: _ CSD Level: ________ DOS Version: ____ DOS Vendor: _________________ Is the failing system a Domain Controller? Y _ N _ Is the failing system an additional server? Y _ N _ DATABASE MANAGER - If this is an OS/2 DATABASE MANAGER problem, please enter information about the DataBase Manager problem below. SQL Error Code ....: ________ Secondary Return Code: ________ Error occurs when database is being accessed as: Stand Alone ......: Y _ N _ Requester (Client): Y _ N _ Database Server ..: Y _ N _ Using RDS ........: Y _ N _ Using LAN ........: Y _ N _ If the error is occurring at a requester, can the problem be recreated at the server? .....: Y _ N _ Error occurs in which application? Query Manager.....: _ LI ..............: _ (Command Line Interface) User Application..: _ If a trap has occurred, provide the SQLABEND results: _________________________________________________________________ _________________________________________________________________ _________________________________________________________________ PLEASE REVIEW ALL OF THIS PROBLEM REPORT BEFORE SENDING. When you are ready to send this OS/2 Problem Report, send the form via CISMAIL to --- Base problems - Base Support, 76711,610 ES/LS problems - ES/LS Support, 76711,611 (ES = IBM Extended Services, LS = IBM LAN Server) Beta problems - 76711,175 (FEEDBACK purposes only...you will not be contacted). (To send from the Internet use address 76711.610@compuserve.com, 76711.611@compuserve.com, or 76711.175@compuserve.com, as appropriate.) Related information: (4.5) Technical Support (4.7) Online Services (4.11) OS/2 BBSes What OS/2 BBSes can I dial? The following BBSes hold large OS/2 libraries: Fernwood (203) 483-0348 OS/2 Shareware (703) 385-4325 Bay Area OS/2 (510) 657-7948 Gateway/2 (314) 554-9313 Greater Chicago Online (708) 895-4042 OS/2 San Diego (619) 558-9475 OS/2 Las Vegas (702) 433-5535 Denver OS/2 BBS (303) 755-6859 OS/2 Source BBS (303) 744-0373 Inside Technologies BBS (313) 283-1151 OS/2 Woodmeister (314) 446-0016 IBM Germany 049-711-785-7777 IBM Denmark 45-42-88-72-22 OS/2 UK 0454-633197 IBM UK 0256-336655 IBM Norway 47-66-99-94-50 OS/2 Norway 47-22-38-09-49 OS/2 Australia 61-2-241-2466 Abaforum (Barcelona, 34-3-589.38.88 Spain) (The monthly Worldwide OS/2 BBS Listing, available from these BBSes, lists others.) The IBM PC Company BBS (modem 404-835-6600) has some shareware/freeware as well, along with CSDs [See (4.6) Corrective Service Diskettes] and the PS/2 Assistant (an invaluable resource for locating almost any sort of information on OS/2). For information on IBM's OS/2 BBS phone 800-547-1283. IBM Canada maintains several support BBSes: (416) 946-4255 (514) 938-3022 (604) 664-6464 (416) 946-4244 Related information: (3.2) Shareware and Freeware Sources (4.6) Corrective Service Diskettes (5.1) Making OS/2 Resemble Unix I'm a Unix wizard. How do I make OS/2 resemble Unix? A great number of GNU and Unix utilities have been ported to OS/2 native mode and are available from (3.2) Shareware and Freeware Sources. A uucp package, UUPC/Extended, is available via anonymous ftp from sun.soe.clarkson.edu, directory pub/uupc; mail help@kew.com with questions. In addition, the Hamilton C Shell is available from Hamilton Labs (phone 508-358-5715 or mail 3890321@mcimail.com). The Thompson Toolkit, a Bourne-like shell, and awk are published by Thompson Automation (phone 206-224-1639). MKS (phone 519-884-2251 or mail pat@mks.com) publishes a number of standard Unix utilities for OS/2. Hippix (Hippo Software; consult file pub/hippo/press.txt, available via anonymous ftp from morgan.cs.utah.edu, for more information) provides a set of low cost Unix-like command utilities (such as grep, awk, sh, and vi) along with a POSIX programming library. For OS/2-specific X-Windows server support, IBM provides an optional package available with its TCP/IP 1.2.1 for OS/2. The TCP/IP 1.2.1 base package includes a news reader as a sample application. DOS and Windows based utilities and aids still work fine under OS/2 2.1. Related information: (3.2) Shareware and Freeware Sources (3.8) Networking Products (5.2) Making OS/2 Resemble Windows I prefer Windows. How do I make OS/2 2.1 resemble Windows (or OS/2 1.3)? Spend some time with the Workplace Shell first. Browse the online Tutorial, Master Help Index, and Start Here facilties. Consult the Unofficial Guide to the Workplace Shell, available from (3.2) Shareware and Freeware Sources. If you still prefer Windows-like behavior, follow the instructions beginning on Page 401 in the OS/2 2.1 Using the Operating System manual. Note that you can run the Win-OS/2 Program Manager "seamlessly" on your OS/2 desktop, and you can use it to launch DOS, Windows, and OS/2 applications. Using the Program Manager in this way can make even hard core Windows users more comfortable. Related information: (3.2) Shareware and Freeware Sources (5.3) Recovering from Crashed Sessions Sometimes OS/2 2.1 will freeze when I run an application. What do I do? Before rebooting with CTRL-ALT-DEL, try CTRL-ESC. Do not hit additional keys, do not move the mouse. Wait up to a minute. Either the Window List or an error message should pop up. You may close the offending application at that point; allow some time for it to close. (Try ALT-ESC if you have disabled CTRL-ESC in that application's DOS Settings. If you do not get any response, press CTRL-ESC or ALT-ESC repeatedly until the dialog appears.) Note that the Workplace Shell can recycle, independent of running applications, if it crashes. If the system is badly disabled, sometimes pressing CTRL-ALT-NUMLOCK twice will result in a prompt to create a dump diskette. You may do so (the online Command Reference describes dump diskettes), or at that point you may reboot with CTRL-ALT-DEL. To prevent applications from automatically restarting see (5.10) Clever Tricks. To restore the desktop to "factory defaults," use ALT-F1 when OS/2 2.1 starts. See Appendix C of the OS/2 2.1 Using the Operating System manual for details. Note that if you have installed an OS/2 Service Pak [See (4.6) Corrective Service Diskettes] the ALT-F1 sequence will restore your desktop to the state it was found in just before installation of the Service Pak. Related information: (4.6) Corrective Service Diskettes (5.10) Clever Tricks (5.4) Starting Background Processes How do I start a background process from the OS/2 command line? Look up the START and DETACH commands in the online Command Reference. If you wish to start a DOS session with nondefault settings, use a utility such as STARTD. If you wish to start an OS/2 session from a DOS session, try OS2EXEC. Both (and several others) are available from (3.2) Shareware and Freeware Sources. Related information: (3.2) Shareware and Freeware Sources (5.5) Adobe Type Manager How do I add new Adobe Type Manager typefaces? (NOTE: The answer to this question may be slightly inaccurate due to minor changes made to Adobe Type Manager under OS/2 2.1. This note will be removed in a future release of the OS/2 Frequently Asked Questions List after any necessary corrections have been made.) OS/2 2.1 comes with built-in Adobe Type Manager (ATM) for OS/2 and Win-OS/2. A basic set of typefaces (Courier, Helvetica, and Times New Roman) comes with OS/2 2.1 and is installed (if selected) for use under both OS/2's and Win-OS/2's ATM. Each typeface should come with three separate files with PFB, AFM, and INF extensions. To install a typeface for use under Win-OS/2, use the ATM Control Panel. The Win-OS/2 ATM Control Panel will then build a PFM file from the INF file. To install a typeface for use with OS/2-specific applications, select OS/2 System -> System Setup -> Font Palette -> Edit Font -> Add. PFM files may converted to AFM files using the PFM2AFM utility, available from (3.2) Shareware and Freeware Sources. (However, these converted AFM files sometimes produce unusual results.) AFM files for Adobe commercial typefaces are available via Internet anonymous ftp from ftp.mv.us.adobe.com. Many public domain typefaces for OS/2's ATM are available from (3.2) Shareware and Freeware Sources. Atech Software's (phone 800-786-FONT) AllType and Ares Software's (phone 415-578-9090) FontMonger convert between TrueType and Adobe Type 1 formats. Typeface files may be shared by OS/2 ATM and Win-OS/2 ATM. To do so, install the typefaces using both the Font Palette and Win-OS/2 ATM Control Panel, specifying the target path each time (most conveniently \PSFONTS). Note that IOPL=YES should appear in CONFIG.SYS; the modules WPPWNDRV, BVHSVGA, and PMATM are marked as requiring I/O privilege. Related information (3.2) Shareware and Freeware Sources (5.6) Performance Tuning How do I tweak OS/2 2.1 for maximum performance? For OS/2 overall, the CONFIG.SYS parameters MAXWAIT, TIMESLICE, PRIORITY, PRIORITY_DISK_IO, PROTECTONLY, and cache settings (in the DISKCACHE line, for FAT; or IFS line, for HPFS) can be tweaked. The swap file should be placed on the most used partition on the least used hard disk, and its location is controlled by the SWAPPATH line. See the online Command Reference for details. FAT partitions should be periodically defragmented. A shareware defragmenter for DOS called DOG (Disk OrGanizer) works well, as do many others. (You can boot DOS from a floppy disk to run such a utility.) For the Workplace Shell, drag shadows of most often used items to the desktop or to folders closer to the "surface" -- opening folders takes time. Drag shadows of program objects you use often (e.g. the Win-OS/2 full screen Program Manager) to the Startup folder. Disable animation (go to OS/2 System -> System Setup -> System -> Window). Use the faster Details View when opening drive and folder objects; to set Details View as the default, open the settings notebook for the object, select the Menu tab, click on ~Open, then the Settings button, then select the Default Action. Try reducing the number of on screen colors or dropping down in screen resolution to enhance speed. Close (not just minimize; check the Window List) unnecessary objects and applications. Use the Monochrome scheme from the Scheme Palette -- it provides marginally faster screen updates. Consider adding more RAM. For DOS programs, run full screen instead of windowed if speed is important. In DOS Settings for each application: reduce conventional, XMS, DPMI, and EMS memory allocations to the bare minimums required for maximum performance; turn off VIDEO_RETRACE_EMULATION unless necessary; adjust IDLE_SENSITIVITY; turn off DOS_BACKGROUND_EXECUTION if not needed; change the HW_TIMER setting (particularly for games); enable VIDEO_FASTPASTE if possible; turn on HW_ROM_TO_RAM. Communications programs should use hardware handshaking where possible (use OS/2's MODE COMx command if necessary), and a buffered UART can prove helpful. (DOS programs running under OS/2 will not be aware of a buffered 16550AF UART. OS/2 virtualizes the serial port and manages the buffer itself.) For faster printing set the DOS program's output port to LPTx.OS2 (where x is the printer port number) -- use a "print to file" option if necessary. Disable any DOS print spoolers; rely on OS/2's spooler instead. Increase CONFIG.SYS's PRINTMONBUFSIZE values. Other, standard steps to enhance DOS performance (e.g. increasing BUFFERS in CONFIG.SYS) of course apply. For Windows programs, run using a full screen desktop if speed is vital. The Win-OS/2 Full Screen icon set up by the installation program has poor Settings. For better performance perform some of the same steps outlined in the preceding paragraph, including VIDEO_RETRACE_EMULATION off. The same printer output advice also applies. Consider disabling the Public setting in the Clipboard. If available, set VIDEO_8514A_XGA_IOTRAP to off. If mouse control is lost when switching to/from the Win-OS/2 session, try setting VIDEO_SWITCH_NOTIFICATION off. Related information: (1.3) DOS and Windows Compatibility (5.7) Measuring Performance and Memory Usage (5.7) Measuring Performance and Memory Usage How do I measure OS/2 performance and memory usage? OS/2 does not treat system resources like DOS. Memory is treated as a virtual resource, used intelligently. For example, OS/2 will retain unused, "dormant" code in memory if that memory is not otherwise required, on the assumption that that code may be used again. Also, all but a small portion of OS/2 (and most applications, no matter how many are running) may be paged to disk should a large amount of physical memory be required. Utilities which display "free" memory, then, are only useful for rough, relative measurements. (Such utilities also often fail for another reason: many only report the largest contiguous block of free physical RAM. And a few will never report more than 16 MB of RAM because they were designed for OS/2 1.x.) Similarly, utilities which purport to measure system load (e.g. Pulse) should not be relied upon for definitive performance measurement. Subjective assessments are often much more reliable. Pulse (and similar utilities) rely on a measurement of processor time allocated to a thread running at OS/2's lowest priority. This method is sometimes subject to erroneous results. That said, more rigorous system performance optimization and monitoring tools include SPM/2 (IBM), BenchTech (Synetik, phone 303-241-1718), and Performance 2.0 (Clear & Simple, phone 203-658-1204). Note that OS/2's swap file is designed to behave with hysteresis. It will not shrink in size as easily as it grows, under the assumption that swap space needed once may be needed again. It should shrink given enough time and continued, less intense system loads. Related information: (5.6) Performance Tuning (5.8) Displaying Background Bitmaps My background bitmap does not display correctly. What's wrong? Color bitmap images used for the Workplace Shell screen or folder backgrounds may not display correctly (may have distorted or missing colors) due to incorrect matching with OS/2's default palette. Unlike Windows, OS/2 does not adjust the palette to accommodate background bitmaps (to keep the rest of the desktop from experiencing color distortions). (Palette control is now available to applications running under the 32-bit graphics engine with an appropriate display driver, however.) To remedy the problem you may use the numerous background images which have been specifically prepared for the Workplace Shell [available from (3.2) Shareware and Freeware Sources] or you may use an image editing/conversion utility which can create a proper, palette-matched bitmap file. For example, FracInt 17.2 [available from (3.2) Shareware and Freeware Sources] may be used to import noninterlaced GIF, Windows BMP, and PCX files and save them as palette matched OS/2 BMP files. Note that background bitmap images impose some additional overhead, taking up RAM and disk resources. You should probably use them sparingly. Also, if you have set a Win-OS/2 background bitmap you may experience desktop color distortions when running Windows programs "seamlessly." Disable the Win-OS/2 background bitmap to remedy the problem. Related information: (2.2) SuperVGA Support (3.2) Shareware and Freeware Sources (5.9) Specific DOS Sessions How do I boot a real version of DOS from within OS/2 2.1? Booting a real version of DOS under OS/2 provides certain features that the OS/2 emulated DOS sessions cannot. For example, a specific DOS session can provide access to devices (like CD-ROM drives) and networks for which there are only DOS device drivers. A specific DOS session can also help get DOS applications which generate spurious "divide by zero" errors running again. You will be able to run one such session per hardware device. So, for example, if you have your DOS networking software loaded in one specific DOS session, you may not start another, similar session. Specific DOS sessions are discussed in the online Command Reference (under VMDISK), the Master Help Index, and the printed Installation Guide (Appendix E). You should consult those resources first. However, if you are still unsure how to configure your system to run specific DOS sessions, follow these steps: 1. Create a bootable DOS diskette. Insert your DOS system diskette into Drive A and reboot. When you arrive at the "A>" prompt, type FORMAT A: /S and press ENTER. (Note that you may wish to format the diskette for the smallest capacity possible, to save hard disk space later on. For example, a 5.25 inch double density -- not high density -- diskette may be formatted to just 160K by adding the /1 /N:8 parameters to the FORMAT command.) When prompted, insert a blank diskette into Drive A and press ENTER. When the FORMAT operation is complete, remove the diskette and restart OS/2. 2. Copy FSFILTER.SYS to the diskette. Double click on OS/2 System -> Command Prompts -> OS/2 Window. Insert the diskette you just formatted into Drive A. Copy the following file to your startable diskette: \OS2\MDOS\FSFILTER.SYS. 3. Set up CONFIG.SYS. Using a text editor (like the OS/2 System Editor) create the file A:\CONFIG.SYS with the following lines at the top: DEVICE=A:\FSFILTER.SYS DEVICE=C:\OS2\MDOS\HIMEM.SYS DEVICE=C:\OS2\MDOS\EMM386.SYS DEVICE=C:\OS2\MDOS\ANSI.SYS Change the "C:" drive letter if OS/2 is installed on another drive. Add any other lines as required for your application (like CD-ROM or networking), but do not include any XMS, EMS, mouse, or memory management device drivers. Make sure that everything is referenced with a drive letter and path, as above. 4. Set up AUTOEXEC.BAT. Likewise, create a file named A:\AUTOEXEC.BAT and make sure that the first line reads: C:\OS2\MDOS\MOUSE changing "C:" if necessary. Add any additional lines (like PATH, SET PROMPT, and so on) as required by your application. 5. Test your DOS diskette. Once you have configured the CONFIG.SYS and AUTOEXEC.BAT files as you wish, double click on OS/2 System -> Command Prompts -> DOS from Drive A:. A DOS session should start. Test for the functionality you need (like access to your CD-ROM reader or network). If the session is not working properly, press CTRL-ESC and shut down the session, edit CONFIG.SYS and/or AUTOEXEC.BAT as required, and repeat the test. 6. Create the diskette image. When you are satisfied that your specific DOS session diskette functions properly, go back to the OS/2 Window and type VMDISK A: C:\DOS.IMG to create a diskette image file. (If you want the file to be located on another drive or in another directory, change "C:\" accordingly.) 7. Create a program object for your specific DOS session. Drag a program object from your Templates folder to any target folder. When the notebook opens, enter a single asterisk (*) in the Program Name field, then click on the right arrow in the lower right. Select either DOS Window or DOS Full Screen for the session type, as desired. Click on the DOS Settings button, and scroll down until you find the DOS_STARTUP_DRIVE property. Enter C:\DOS.IMG in the field at the upper right. (If your image file is not located on Drive C in the root directory, make the necessary changes.) Change any other DOS Settings if necessary. Click on the Save button, then click on the General tab. Give your program object a name. Then close up the notebook. You should now be able to double click on your new program object to start your specific DOS session. If you require access to your diskette drive (Drive A), use the FSACCESS command. See the online Command Reference for details. When formatting your bootable DOS diskette, you may wish to use additional command line parameters to create a diskette with a reduced capacity. The "smaller" the diskette, the less room the diskette image file created by VMDISK will take on your hard disk. See your DOS manual for details, or use the example given above. Related information: (1.3) DOS and Windows Compatibility (5.10) Clever Tricks Are there any clever tricks that apply to OS/2 2.1? o To force DIR to display your directories in alphabetical order, with the subdirectories listed first, add the line SET DIRCMD=/O:GN to CONFIG.SYS; and, if you wish the same for your DOS command line sessions, add the same line to AUTOEXEC.BAT. You may also wish to run DOSKEY to enable the command history feature. (Shutdown and reboot for changes to CONFIG.SYS to take effect.) o Hold down SHIFT while resizing text windows to make size changes permanent. o If you want to configure your printer port(s) for shared access (so that DOS programs, for example, can use them directly), go to your printer object, click on it with mouse button two, select Open -> Settings, select the Output tab, then double click on the port you wish to share. Check the appropriate box. o While running a DOS graphics program in a window, use the graphics cut and paste feature to clip a picture and paste it into the Icon Editor. You can then quickly and easily create custom icons for your applications. o To disable the automatic application restart feature, create a STARTUP.CMD file in the root directory of your OS/2 boot drive with the following REXX script: /* */ call RxFuncadd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs' call SysLoadFuncs call SysIni 'USER', 'PM_WorkPlace:Restart', 'DELETE:' 'exit' or add the line SET RESTARTOBJECTS=STARTUPFOLDERSONLY to your CONFIG.SYS. To manually disable automatic application restart when booting OS/2, hold down the left CTRL, left SHIFT, and F1 keys simultaneously from the time the mouse pointer appears until icons are displayed on the desktop. o Use the Alarms applet to automatically start programs at specified times. To start the Alarms applet minimized, put /I in the Optional Parameters section of its program object settings. o If you wish to dispense with the Workplace Shell (and its overhead), particularly on low memory systems, change the line SET RUNWORKPLACE... in CONFIG.SYS to read SET RUNWORKPLACE=C:\OS2\CMD.EXE (replacing C, if necessary, with a different drive letter). In fact any program with job control (e.g. Enhanced Editor, HyperAccess/5) can be used as the shell. o To implement a small scroll back buffer for your OS/2 command line windows, use the command MODE CO80,102. This procedure may be automated by adding /K MODE CO80,102 in the Optional Parameters section of the OS/2 Window program object settings. o If you do not want any command line parameters passed to a program object that you start (for example, if you customize the desktop menu so that it has an additional option which starts a command line prompt) place a lone % in the Optional Parameters section of the program object settings. If you do wish to pass parameters, but you want the extraneous information that the Workplace Shell passes to the object to be ignored, try putting && REM % in the Optional Parameters section. [Continue with Part 4 of 4.] -- Timothy F. Sipples |READ the OS/2 FAQ List 2.1A, available from sip1@kimbark.uchicago.edu|192.153.46.254, anonymous ftp, in /os2/all/info/faq, Dept. of Econ., Univ. |or from LISTSERV@BLEKUL11.BITNET (send "HELP"). of Chicago, 60637 |[Post to ONE newsgroup only AFTER reading the List.]